Methods and Systems for Query Resolution Through Graphical User Interfaces

ABSTRACT

Methods and systems for query resolution through graphical user interfaces are disclosed. In one aspect, a system is disclosed that includes a processor and data storage including instructions that, when executed by the processor, cause the system to perform operations. The operations include receiving a query requesting resolution of inconsistent data; based on the query, creating an instance in a queue, where the instance identifies a priority and a task for the query; based on the priority, selecting the query from the queue and initiating resolution of the inconsistent data by generating a graphical user interface to accomplish the task; while accomplishing the task, generating each of (i) a documentation documenting the inconsistent data and the task and (ii) a resolution resolving the inconsistent data; storing the documentation; and publishing the resolution.

BACKGROUND

In some cases, inconsistencies may appear in data dispersed betweenmultiple entities. For example, a first entity may maintain first datathat is inconsistent with second data maintained by a second entity. Asanother example, the first entity may dispute data maintained by thesecond entity.

When inconsistencies appear in dispersed data, no single entity may havesufficient information to resolve the inconsistent data and, moreover,the entities may be ill-equipped to communicate data among one another.For example, a first entity may be unable to access second datamaintained by a second entity, and the second entity may be unable toaccess first data maintained by the first entity. As another example,the first entity may be unable to access data maintained by the secondentity.

In some cases, a third-party system may assist in resolving inconsistentdata by collecting data from multiple entities. For example, athird-party system may collect data from each of a first entity and asecond entity and, based on the collected data, resolve the inconsistentdata. However, current third-party systems provide only limited insightsinto how a resolution is reached.

SUMMARY

The disclosed embodiments describe systems and methods for queryresolution through graphical user interfaces.

In one aspect, a system is disclosed that includes a processor and datastorage including instructions that, when executed by the processor,cause the system to perform operations. The operations include receivinga query from a querying entity requesting resolution of inconsistentdata; based on the query, creating an instance in a queue, where theinstance identifies a priority and a task for the query; based on thepriority, selecting the query from the queue and initiating resolutionof the inconsistent data by generating a graphical user interface toaccomplish the task, where the graphical user interface is configured toreceive an input associated with the task; while accomplishing the task,generating each of (i) a documentation documenting the inconsistentdata, the task, and the input and (ii) a resolution resolving theinconsistent data; storing the documentation; and publishing theresolution.

In another aspect, a system is disclosed that includes a processor anddata storage including instructions that, when executed by theprocessor, cause the system to perform operations. The operationsinclude maintaining a queue including a plurality of queries requestingresolution of inconsistent data; selecting a query from the plurality ofqueries and identifying a task for the selected query; based on thetask, generating a graphical user interface configured for resolution ofthe inconsistent data; receiving, through the graphical user interface,an input associated with the task; providing, through the graphical userinterface, an output associated with the task; generating each of (i) adocumentation documenting the inconsistent data, the task, the input,and the output, and (ii) a resolution resolving the inconsistent data;storing the documentation; and publishing the resolution.

Aspects of the disclosed embodiments may include non-transitory,tangible computer-readable media that store software instructions that,when executed by one or more processors, are configured for and capableof performing and executing one or more of the methods, operations, andthe like consistent with the disclosed embodiments. Also, aspects of thedisclosed embodiments may be performed by one or more processors thatare configured as special-purpose processor(s) based on softwareinstructions that are programmed with logic and instructions thatperform, when executed, one or more operations consistent with thedisclosed embodiments.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate disclosed embodiments and,together with the description, serve to explain the disclosedembodiments. In the drawings:

FIG. 1 is a block diagram of an exemplary system, consistent withdisclosed embodiments.

FIG. 2 is a block diagram of an exemplary resolution system, consistentwith disclosed embodiments.

FIG. 3 is a flowchart of an exemplary resolution process, consistentwith disclosed embodiments.

FIG. 4 is a flowchart of another exemplary resolution process,consistent with disclosed embodiments.

FIG. 5 illustrates an exemplary resolution process, consistent withdisclosed embodiments.

FIGS. 6A-6E illustrate exemplary graphical user interfaces in aresolution process, consistent with disclosed embodiments.

FIG. 7 illustrates an exemplary documentation generated through aresolution process, consistent with disclosed embodiments.

FIG. 8 illustrates an exemplary resolution generated through aresolution process, consistent with disclosed embodiments.

DETAILED DESCRIPTION

Reference will now be made in detail to the disclosed embodiments,examples of which are illustrated in the accompanying drawings.

The disclosed systems, methods, and media describe systems and methodsfor query resolution through graphical user interfaces. In someembodiments, a query may be a query requesting resolution ofinconsistent data. For example, a query may request resolution ofinconsistent data included in a credit history or other record. In someembodiments, a query may be received from a querying entity, such as anindividual other entity and/or one or more computing devices associatedwith an individual or other entity. For example, a query may be receivedfrom an individual associated with a credit history or other record. Asanother example, a query may be received from a credit reporting agency(e.g., Equifax, Experian, Innovis, or Transunion) or a credit datafurnisher (e.g., a financial service provider) associated with a credithistory or other record. Upon receipt of a query, the disclosed systemsand methods generate graphical user interfaces through which one or moretasks may be accomplished to resolve the inconsistent data. Thedisclosed systems and methods may generate a resolution resolving theinconsistent data that may be published to the querying entity. Inaddition, the disclosed systems and methods may generate a documentationdocumenting the inconsistent data and the task that may be stored. Thedocumentation may document how the inconsistent data was resolved.

Documentation and resolutions generated by the disclosed methods andsystems may describe numerous aspects of the resolution process,including the query, the querying entity, the inconsistent data, tasksperformed to resolve the inconsistent data, graphical user interfacesgenerated to accomplish the tasks, information retrieved to accomplishthe tasks, and inputs received and/or outputs provided through thegraphical user interfaces. As a result, compared to current third-partysystems for resolving inconsistent data, the documentation andresolutions generated by the disclosed methods and systems provideimproved insights into how a resolution is reached.

FIG. 1 is a block diagram of an exemplary system 100, consistent withdisclosed embodiments. System 100 may be configured for performing aresolution process consistent with disclosed embodiments.

As shown, system 100 may include one or more querying entities 102, aresolution system 104, one or more data source(s) 106, and data storage108. As shown, querying entities 102, resolution system 104, datasource(s) 106, and data storage 108 may be communicatively coupled by anetwork 110.

While only one resolution system 104 is shown, it will be understoodthat system 100 may include more than one resolution system 104 as well.Further, while certain numbers of querying entities 102, data source(s)106, and data storage 108 are shown, it will be understood that system100 may include more or fewer of these components as well. Moregenerally, the components and arrangement of the components included insystem 100 may vary. Thus, system 100 may include other components thatperform or assist in the performance of one or more processes consistentwith the disclosed embodiments.

Querying entities 102 may be one or more individuals, companies, and/orother entities (and/or one or more computing devices associated withsuch entities) from resolution system 104 receives queries. A query may,for example, request resolution of inconsistent data.

In some embodiments, a querying entity 102 may submit a query toresolution system 104 over network 110. For example, querying entity 102may include and/or may be associated with a communication deviceconfigured to send the query to resolution system 104 over network 110.Alternatively or additionally, a querying entity 102 may submit a queryto resolution system 104 over another communicative link, such as apaper-based connection (e.g., mail or fax) or a telephone connectiondistinct from network 110.

The query may be sent by a querying entity 102 as an individual queryand/or as part of a batch process. For example, the query may be sent byquerying entity 102 upon detection of inconsistent data. In someembodiments, querying entity 102 may be an individual, and theindividual may send the query to resolution system 104 using a computingdevice (e.g., through a website or mobile application or by e-mail), bymail or fax, and/or by telephone upon detection of inconsistent data. Asanother example, the query may be sent by querying entity 102 with abatch periodically, upon collecting a threshold number of queries,and/or upon request of resolution system 104. In some embodiments,querying entity 102 may be a system configured to aggregate queries,such as the eOscar® system developed by Equifax, Experian, Innovis, andTransUnion. Such a querying entity 102 may be configured to send queriesto resolution system 104 upon detection of inconsistent data or as partof a batch process executed at querying entity 102.

In some embodiments, a querying entity 102 may receive a resolutionresolving the inconsistent data in the query from resolution system 104.The resolution may be generated through a resolution process atresolution system 104, as described below. In some embodiments, aquerying entity 102 may receive the resolution over network 110 or overanother communicative link, such as a paper-based connection (e.g., mailor fax) or a telephone connection distinct from network 110.

The resolution may be received by a querying entity 102 as an individualresolution and/or as part of a batch process. For example, theresolution may be received by querying entity 102 upon resolution of thequery. In some embodiments, querying entity 102 may be an individual,and the individual may receive the resolution from resolution system 104using a computing device (e.g., through a website or mobile applicationor by e-mail), by mail or fax, and/or by telephone upon resolution ofthe query. As another example, the resolution may be received byquerying entity 102 with a batch periodically, upon collecting athreshold number of resolutions, and/or upon request of querying entity102. In some embodiments, querying entity 102 may be a system configuredto aggregate queries, such as the eOscar® system developed by Equifax,Experian, Innovis, and TransUnion. Such a querying entity 102 may beconfigured to receive resolutions from resolution system 104 uponresolution of each query or as part of a batch process executed atresolution system 104.

Resolution system 104 may be one or more computing devices configured toprovide a resolution process as described herein. In some embodiments,resolution system 104 may be configured to receive queries from queryingentities 102, as described above. For example, resolution system 104 maybe configured to receive a query over network 110 and/or anothercommunicative link distinct from network 110. For example, resolutionsystem 110 may receive a query electronically (e.g., through a websiteor mobile application or by e-mail). As another example, resolutionsystem 110 may receive a query over a paper-based connection (e.g., mailor fax) or a telephone connection distinct from network 110. In someembodiments, resolution system 110 may be configured to use opticalcharacter recognition and/or voice recognition to process queriesreceived over a paper-based and/or telephone connection. For example,where a query is received as a letter from a querying entity 102,resolution system 104 may be configured to use an optical characterrecognition process to process the letter and determine the query. Asanother example, where a query is received by a telephone call from aquerying entity 102, resolution system 104 may be configured to use avoice recognition process to process the telephone call and determinethe query.

Resolution system 104 may receive queries individually and/or through abatch process. For example, the query may be received from queryingentity 102 upon detection of inconsistent data by querying entity 102.In some embodiments, querying entity 102 may be an individual, and theindividual may send the query to resolution system 104 using a computingdevice (e.g., through a website or mobile application or by e-mail), bymail or fax, and/or by telephone upon detection of inconsistent data. Asanother example, the query may be received from querying entity 102 in abatch periodically, upon querying entity 102 collecting a thresholdnumber of queries, and/or upon request of resolution system 104. In someembodiments, querying entity 102 may be a system configured to aggregatequeries, such as the eOscar® system developed by Equifax, Experian,Innovis, and TransUnion. Resolution system 104 may receive queries fromsuch a querying entity 102 upon detection of inconsistent data atquerying entity 102 or as part of a batch process executed at queryingentity 102.

Resolution system 104 may be further configured to perform a resolutionprocess, such as the resolution processes described below in connectionwith FIGS. 3 and 4. In some embodiments, to perform the resolutionprocess, resolution system 104 may obtain information for use in theresolution process from one or more data source(s) 106. Information mayinclude, for example, information associated with querying entity 102.

Data source(s) 106 may include one or more computing devices configuredto maintain information for use in a resolution process. In someembodiments, one or more data source(s) 106 may take the form of serversor databases, such as Oracle™ databases, Sybase™ databases, or otherrelational databases or non-relational databases, such as Hadoopsequence files, HBase, or Cassandra. Such database(s) may includecomputing components (e.g., database management system, database server,etc.) configured to receive and process requests for data stored inmemory devices of the database(s) and to provide data from thedatabase(s). Alternatively or additionally, data source(s) 106 mayinclude cloud-based storage accessible by resolution system 104 overnetwork 110 and/or another network.

In some embodiments, data source(s) 106 may aggregate information fromone or more sources, such as one or more servers in network 110 and/orsystem 100. Alternatively or additionally, data source(s) 106 may beincluded in and/or otherwise associated with one or more such sources.In some embodiments, data source(s) 106 may aggregate data from, may beincluded in, and/or may be otherwise associated with a financial serviceentity that provides, maintains, manages, or otherwise offers financialservices. For example, the financial service entity may be a bank,credit card issuer, or any other type of financial service entity thatgenerates, provides, manages, and/or maintains user accounts for one ormore customers. In some embodiments, user accounts may include, forexample, credit card accounts, loan accounts, checking accounts, savingsaccounts, reward or loyalty program accounts, and/or any other type offinancial service account. As another example, the financial serviceentity may be a credit reporting agency (e.g., Equifax, Experian,Innovis, or Transunion), a credit data furnisher (e.g., a financialservice provider), or other type of financial service entity thatgenerates, manages, and/or maintains credit ratings and/or creditreports for individuals. While data source(s) 106 are shown separately,in some embodiments some or all of data source(s) 106 may be included inand/or otherwise associated with resolution system 104, data storage108, and/or another entity in network 110 and/or system 100.

In some embodiments, to perform the resolution process, resolutionsystem 104 may further generate a resolution resolving the inconsistentdata indicated in the query. An example resolution is further describedbelow in connection with FIG. 7. The resolution may be published byresolution system 104 by, for example, sending the resolution toquerying entity 102.

In some embodiments, resolution system 104 may send the resolution toquerying entity 102 over network 110 or over another communicative link,such as a paper-based connection (e.g., mail or fax) or a telephoneconnection distinct from network 110. The resolution may be sent toquerying entity 102 as an individual resolution and/or as part of abatch process. For example, the resolution may be sent to queryingentity 102 upon resolution of the query. In some embodiments, queryingentity 102 may be an individual, and resolution system 104 may send theresolution to the individual through a website or mobile application orby e-mail, by mail or fax, and/or by telephone upon resolution of thequery. As another example, resolution system 104 may send the resolutionto querying entity 102 with a batch periodically, upon collecting athreshold number of resolutions, and/or upon request of querying entity102. In some embodiments, querying entity 102 may be a system configuredto aggregate queries, such as the eOscar® system developed by Equifax,Experian, Innovis, and TransUnion. Resolution system 104 may beconfigured to send resolutions to such a querying entity 102 uponresolution of each query or as part of a batch process executed atresolution system 104.

In some embodiments, to perform the resolution process, resolutionsystem 104 may further generate a documentation describing theresolution process. An example documentation is further described belowin connection with FIG. 8. The documentation may be stored in datastorage 108.

Data storage 108 may include one or more memory devices that storeinformation and are accessed and/or managed through resolution system104. By way of example, data storage 108 may include one or moredatabase(s), such as Oracle™ databases, Sybase™ databases, or otherrelational databases or non-relational databases, such as Hadoopsequence files, HBase, or Cassandra. Such database(s) may includecomputing components (e.g., database management system, database server,etc.) configured to receive and process requests for data stored inmemory devices of the database(s) and to provide data from thedatabase(s). Alternatively or additionally, data storage 108 may includecloud-based storage accessible by resolution system 104 over network 110and/or another network. While data storage 108 is shown separately, insome embodiments data storage 108 may be included in and/or otherwiseassociated with resolution system 104, data source(s) 108, and/oranother entity in network 110 and/or system 100.

Network 110 may be any type of network configured to providecommunication between components of system 100. For example, network 110may be any type of network (including infrastructure) that providescommunications, exchanges information, and/or facilitates the exchangeof information, such as the Internet, a Local Area Network, near fieldcommunication (NFC), optical code scanner, or other suitableconnection(s) that enables the sending and receiving of informationbetween the components of system 100. In other embodiments, one or morecomponents of system 100 may communicate directly through a dedicatedcommunication link(s).

It is to be understood that the configuration and boundaries of thefunctional building blocks of system 100 have been defined herein forthe convenience of the description. Alternative boundaries may bedefined so long as the specified functions and relationships thereof areappropriately performed. Alternatives (including equivalents,extensions, variations, deviations, etc., of those described herein)will be apparent to persons skilled in the relevant art(s) based on theteachings contained herein. Such alternatives fall within the scope andspirit of the disclosed embodiments.

FIG. 2 is a block diagram of an exemplary resolution system 200,consistent with disclosed embodiments. As shown, resolution system 200may include a communication device 202, one or more processor(s) 204,and memory 206 including one or more program(s) 208 and data 210.

Resolution system 200 may take the form of a server, general purposecomputer, mainframe computer, or any combination of these components.Other implementations consistent with disclosed embodiments are possibleas well. Resolution system 200 may, for example, be similar toresolution system 104 described above.

Communication device 202 may be configured to communicate with one ormore entities. For example, in some embodiments, communication device202 may be configured to communicate with one or more querying entities,such as querying entities 102 described above. In some embodiments,communication device 204 may be configured to communicate with thequerying entities through a network, such as network 110 describedabove. Alternatively or additionally, communication device 204 may beconfigured to communicate with the querying entities through a web page,a mobile application, and/or e-mail. In some embodiments, communicationdevice 204 may be configured to communicate with the querying entitiesthrough an optical character recognition and/or voice recognitionprocess. Communication device 204 may communicate with the queryingentities in other manners as well.

Communication device 202 may be configured to communicate with thequerying entities to, for example, receive queries. The queries may bequeries for resolution of inconsistent data. Communication device 202may receive the queries individually and/or through a batch process, asdescribed above. Communication device 204 may be further configured tocommunicate with the querying entities to, for example, publishresolutions generated by a resolution process, such as the resolutionsprocesses described below in connection with FIGS. 3 and 4. Theresolutions may resolve the inconsistent data associated with queries.Communication device 202 publish the resolutions individually and/orthrough a batch process, as described above.

In some embodiments, communication device 202 may be further configuredto communicate with one or more data sources, such as data source(s) 106described above. For example, resolution system 200 may be configured toobtain from the data sources, via communication device 202, informationassociated with the query, such as information associated with thequerying entity and/or the inconsistent data, in connection with aresolution process, such as the resolutions processes described below inconnection with FIGS. 3 and 4.

Alternatively or additionally, in some embodiments, communication device202 may be configured to communicate with data storage, such as datastorage 108 described above. For example, resolution system 200 may beconfigured to store in data storage documentations and/or resolutionsgenerated during a resolution process, such as the resolutions processesdescribed below in connection with FIGS. 3 and 4.

Communication device 202 may also be configured to communicate withother components. In general, communication device 202 may be configuredto provide communication over a network, such as network 110 describedabove. To this end, communication device 202 may include, for example,one or more digital and/or analog devices that allow resolution system200 to communicate with and/or detect other components, such as anetwork controller and/or wireless adaptor for communicating over theInternet. Other implementations consistent with disclosed embodimentsare possible as well.

Processor(s) 204 may include one or more known processing devices, suchas a microprocessor from the Core™, Pentium™ or Xeon™ familymanufactured by Intel™, the Turion™ family manufactured by AMD™, the“Ax” or “Sx” family manufactured by Apple™, or any of various processorsmanufactured by Sun Microsystems, for example. The disclosed embodimentsare not limited to any type of processor(s) otherwise configured to meetthe computing demands required of different components of resolutionsystem 200.

Memory 206 may include one or more storage devices configured to storeinstructions used by processor(s) 204 to perform functions related todisclosed embodiments. For example, memory 206 may be configured withone or more software instructions, such as program(s) 208, that mayperform one or more operations when executed by processor(s) 204. Thedisclosed embodiments are not limited to separate programs or computersconfigured to perform dedicated tasks. For example, memory 206 mayinclude a single program 208 that performs the functions of resolutionsystem 200, or program(s) 208 may comprise multiple programs. Memory 206may also store data 210 that is used by program(s) 208. In someembodiments, for example, data 210 may include queries, information foruse in a resolution process, such as the resolution process describedbelow in connection with FIGS. 3 and 4, and documentations, and/orresolutions generated through a resolution process, such as theresolution process described below in connection with FIGS. 3 and 4.Other data 210 is possible as well.

In certain embodiments, memory 206 may store sets of instructions forcarrying out the resolution processes described below in connection withFIGS. 3 and 4. For example, as shown, memory 206 may include aresolution program 214 configured to generate resolutions and adocumentation program 216 configured to generate documentations inconnection with a resolution process, such as the resolution processdescribed below in connection with FIGS. 3 and 4. Other instructions arepossible as well. In general, instructions may be executed byprocessor(s) 206 to perform one or more processes consistent withdisclosed embodiments.

The components of resolution system 200 may be implemented in hardware,software, or a combination of both hardware and software, as will beapparent to those skilled in the art. For example, although one or morecomponents of resolution system 200 may be implemented as computerprocessing instructions, all or a portion of the functionality ofresolution system 200 may be implemented instead in dedicatedelectronics hardware.

Resolution system 200 may include more, fewer, and/or differentcomponents than those shown. For example, in some embodiments,resolution system 200 may include and/or may be communicatively coupledto one or more display devices configured to provide output and/ordisplay graphical user interfaces, such as the graphical user interfacesdescribed below in connection with FIGS. 6A-6E. In some embodiments,such a display device may include a screen for displaying a graphicaland/or text-based user interface, including but not limited to, liquidcrystal displays (LCD), light emitting diode (LED) screens, organiclight emitting diode (OLED) screens, and other known display devices. Asanother example, in some embodiments resolution system 200 may includeand/or may be communicatively coupled to one or more digital and/oranalog devices configured to receive input, such as a touch-sensitivearea, keyboard, buttons, or microphones. Other components are possibleas well.

FIG. 3 is a flowchart of an exemplary resolution process 300, consistentwith disclosed embodiments. Resolution process 300 may be carried out bya resolution system, such as resolution systems 104 and 200 describedabove.

As shown in FIG. 3, resolution process 300 includes at step 302receiving a query for a resolution and assigning the query to a queue.The query may be, for example, a query for resolution of inconsistentdata. In some embodiments, the query may be received from a queryingentity, such as any of querying entities 102 described above. Forexample, the query may be received from an individual and may requestresolution of inconsistent data included in a credit history for theindividual. As another example, the query may be received from a creditreporting agency, a credit data furnisher, or another entity and mayrequest resolution of inconsistent data associated with a potentialfraud. The query may be received in any of the manners described abovein connection with communication device 202.

At step 304, resolution process 300 further includes, based on thequery, creating an instance in a queue, where the instance identifies apriority and a task for the query. The task may describe information,inputs, and/or outputs through which the inconsistent data may beresolved. For example, the task may describe information to be retrievedby the resolution system to resolve the inconsistent data, such asinformation from data storage (e.g., data storage 108 described above)and/or one or more remote entities (e.g., data source(s) 106 describedabove). As another example, the task may describe inputs to be receivedand/or outputs to be provided, such as through a graphical userinterface, to resolve the inconsistent data. The inputs and/or outputsmay be received from and/or provided to, for example, an operator of theresolution system. The instance may identify a single task forresolution of the inconsistent data, or the instance may identifymultiple tasks for resolution of the inconsistent data.

The priority may indicate a priority with which the query is to beresolved by the resolution system relative to other queries. In someembodiments, the priority may be identified based on a date the query isreceived. For example, the queue may be a first-in-first-out queue or alast-in-first-out queue. As another example, a deadline for resolvingthe query may be determined based on the date the query is received, andthe priority may identified based on the deadline (e.g., queries withsooner deadlines may have higher priority than queries with laterdeadlines). Alternatively or additionally, the priority may beidentified based on the identified task. For example, a higher prioritymay be identified for certain tasks than for others (e.g., simpler tasksmay be assigned a higher priority than more complex tasks). Stillalternatively or additionally, identifying the priority may rely inwhole or in part on randomization. The priority may be identified inother manners as well.

In some embodiments, the resolution system may maintain the queue indata storage, such as data storage 108 or data 210 described above. Theresolution system may maintain a single queue for queries or maymaintain more than one queue. In some embodiments, the resolution systemmay assign the query to a queue based on the query, the querying entity,and/or the inconsistent data. Alternatively or additionally, theresolution system may assign the query to a queue based on the priorityand/or the task identified for the query. The resolution system mayassign the query in other manners as well.

At step 306, resolution process 300 further includes, based on thepriority, selecting the query from the queue and initiating resolutionof the inconsistent data by generating a graphical user interface toaccomplish the task. In some embodiments, the graphical user interfacemay be configured to, for example, receive inputs and/or provide outputsaccording to the task to resolve the inconsistent data. For example, thegraphical user interface may include a field, drop-down menu, or otherinput mechanism to receive an input associated with the task. As anotherexample, the graphical user interface may be include a text-based and/orgraphic output mechanism to provide an output associated with the task.The inputs and/or outputs may be received from and/or provided to, forexample, an operator of the resolution system.

In some embodiments, accomplishing the task may involve the resolutionsystem retrieving information from data storage (e.g., data storage 108described above) and/or one or more remote entities (e.g., datasource(s) 106 described above). The graphical user interface may beconfigured to display and/or may be otherwise based on the retrievedinformation. For example, the graphical user interface may include atext-based and/or graphic representation (e.g., image, chart, graph,etc.) of some or all of the retrieved information. Example graphicaluser interfaces are further described below in connection with FIGS.6A-6E.

Resolution process 300 further includes, at step 308, whileaccomplishing the task, generating each of a documentation and aresolution. The documentation may be a documentation describing theinconsistent data and/or the task. An example documentation is furtherdescribed below in connection with FIG. 8. The resolution may be aresolution resolving the inconsistent data. An example resolution isfurther described below in connection with FIG. 7. The documentationand/or the resolution may include text-based and/or graphicrepresentations (e.g., images, charts, graphs, etc.) based on theinconsistent data, the task, the resolution, any retrieved information,any inputs and/or outputs, and/or any generated graphical userinterfaces.

In some embodiments, as noted above, accomplishing the task may involvethe resolution system retrieving information from data storage (e.g.,data storage 108 described above) and/or one or more remote entities(e.g., data source(s) 106 described above). The documentation and/or theresolution may include, may describe, and/or may be based on theretrieved information as well.

Alternatively or additionally, in some embodiments, as described above,accomplishing the task may involve the resolution system receivinginputs and/or providing outputs through a graphical user interfaceaccording to the task to resolve the inconsistent data. Thedocumentation and/or the resolution may include, may describe, and/ormay be based on the inputs, the outputs, and/or the graphical userinterface.

Resolution process 300 further includes, at step 310, storing thedocumentation. The resolution system may store the documentation in, forexample, data storage (e.g., data storage 108 described above) and/or atone or more remote entities (e.g., data source(s) 106 described above).In some embodiments, the documentation may be searchable and/orretrievable based on some or all of the contents of the documentation.For example, the documentation may be searchable based on the query, theinconsistent data, the priority, the task, any retrieved information,inputs, and/or outputs used to accomplish the task, and/or theresolution. The documentation may be searchable based on otherinformation as well, such as an operator from whom input was receivedand/or a remote entity from which information was received. In someembodiments, the data storage and/or remote entity storing thedocumentation may include computing components (e.g., management system,server, etc.) configured to receive and process requests for stored dataand to provide data from the database(s).

Resolution process 300 further includes, at step 312, publishing theresolution. The resolution system may publish the resolution to, forexample, the querying entity and/or one or more other entities. Forexample, the resolution system may publish the resolution to a remoteentity from which information was retrieved to accomplish the task. Asanother example, where the query requested resolution of inconsistentdata included in an individual's credit history, the resolution may bepublished to the individual, a credit reporting agency, a credit datafurnisher, and/or another entity. The resolution may be published in anyof the manners described above in connection with communication device202.

Publishing the resolution may involve sending the resolution (e.g., bye-mail, mail, fax, telephone, etc.) and/or making the resolutionavailable (e.g., through a webpage and/or mobile application). Forexample, in some embodiments publishing the resolution may involvegenerating a documentation describing the resolution and sending and/ormaking available the documentation. The resolution may be published inother manners as well.

While the foregoing described the documentation as being stored and theresolution as being published, in some embodiments the documentation mayalternatively or additionally be published, and the resolution mayalternatively or additionally be stored.

FIG. 4 is a flowchart of another exemplary resolution process 400,consistent with disclosed embodiments. Resolution process 400 may becarried out by a resolution system, such as resolution systems 104 and200 described above.

As shown in FIG. 4, resolution process 400 includes at step 402maintaining a queue including a plurality of queries requestingresolution of inconsistent data. The queries may take any of the formsdescribed above. The queries may be received from the same queryingentity and/or from multiple querying entities. The queries may have beenreceived by resolution system in any of the manners described above inconnection with communication device 202.

Resolution process 400 further includes, at step 404, selecting a queryfrom the plurality of queries and identifying a task for the selectedquery. In some embodiments, the resolution system may select theselected query based on a priority identified for the query. Thepriority may be identified in any of the manners described above inconnection with resolution process 300. Alternatively or additionally,in some embodiments the resolution system may select the selected querybased in whole or in part on randomization. Still alternatively oradditionally, in some embodiments the resolution system may select theselected query in whole or in part based on input received from anoperator of the resolution system (e.g., the operator may select thequery or a querying entity from a drop-down menu or the operator mayindicate a type of inconsistent data). The query may be selected inother manners as well.

The resolution system may identify a task for the selected query basedon the selected query, the querying entity, and/or the inconsistentdata. In some embodiments, the task may be identified based on anoptical character and/or voice recognition process. For example, thequery may be received by mail, and an optical character recognitionprocess may be used to recognize characters included in the query. Basedon the recognized query, the resolution system may identify the queryingentity and the inconsistent data and, based on the querying entityand/or the inconsistent data, identify a task.

At step 406, resolution process further includes, based on the task,generating a graphical user interface configured for resolution of theinconsistent data. The graphical user interface may take any of theforms described above in connection with resolution process 300. Examplegraphical user interfaces are further described below in connection withFIGS. 6A-6E.

Resolution process 400 further includes, at step 408, receiving, throughthe graphical user interface, an input. The input may be received from,for example, an operator of the resolution system. In some embodiments,the graphical user interface may be configured to, for example, receiveinputs according to the task to resolve the inconsistent data. Forexample, the graphical user interface may include a field, drop-downmenu, or other input mechanism to receive an input associated with thetask. Inputs are further described below in connection with the examplegraphical user interfaces of FIGS. 6A-6E.

Resolution process 400 further includes, at step 410, providing, throughthe graphical user interface, an output. The output may be provided to,for example, an operator of the resolution system. In some embodiments,the graphical user interface may be configured to, for example, providethe outputs according to the task to resolve the inconsistent data. Forexample, the graphical user interface may include a text-based and/orgraphic output mechanism to provide an output associated with the task.Outputs are further described below in connection with the examplegraphical user interfaces of FIGS. 6A-6E.

In some embodiments, accomplishing the task may involve the resolutionsystem retrieving information associated with the selected query fromdata storage (e.g., data storage 108 described above) and/or one or moreremote entities (e.g., data source(s) 106 described above), as describedabove. In some embodiments, the graphical user interface, the inputs,and/or the outputs may be based on the retrieved information.

Resolution process 400 further includes, at step 412, generating adocumentation and a resolution. The documentation and the resolution maytake any of the forms described above in connection with resolutionprocess 300. In some embodiments, the documentation and/or theresolution may be published and/or stored, as described above inconnection with resolution process 300.

FIG. 5 illustrates an exemplary resolution process, consistent withdisclosed embodiments. While the resolution process is described withrespect to resolution system 500, first querying entity 502, secondquerying entity 504, data source(s) 506, and data storage 508, it willbe understood that other resolution systems, querying entities, datasources, and data storage are possible as well.

Resolution system 500 may take any of the forms described above forresolution systems 104 and 200. Resolution system 500 may be configuredto maintain one or more queues including queries. The queues may bemaintained at resolution system 500 and/or in data storage accessible byresolution system 500, such as data storage 508.

As shown, resolution system 500 may receive a first query 502A fromfirst querying entity 502. Resolution system 500 may further receive asecond query 504A from second querying entity 504. First querying entity502 and second querying entity 504 may take any of the forms describedabove for querying entities 102.

First query 502A may be a query requesting resolution of inconsistentdata. For example, first querying entity 502 may be an individual, andfirst query 502A may be a query requesting resolution of inconsistentdata on the individual's credit history. First query 502A may bereceived through, for example, a webpage or a mobile application.Alternatively, first query 502A may be received by mail, by fax, or bytelephone. In some embodiments, resolution system 500 may identify thesecond querying entity 504, the inconsistent data, a task, and/or apriority for first query 502A, as described above. For example,resolution system 500 may use optical character and/or voice recognitionto identify the first querying entity 502, the inconsistent data, atask, and/or a priority for first query 502A. For example, resolutionsystem 500 may use optical character recognition to identifyinconsistent data, such as a credit inquiry or a late payment on acredit card the individual claims did not occur. As another example,resolution system 500 may use voice recognition to identify a task byrecognizing key words used in the query.

Second query 504A may be a query requesting resolution of inconsistentdata. For example, second querying entity 504 may be a system configuredto aggregate queries, such as the eOscar® system developed by Equifax,Experian, Innovis, and TransUnion, and second query 504A may be a queryreceived through a batch process at second querying entity 504. Secondquery 504A may request resolution of inconsistent data, such as atransaction claimed to be fraudulent by an individual. In someembodiments, second querying entity 504 may have received the query fromthe individual and/or a credit data furnisher. In some embodiments,resolution system 500 may identify the second querying entity 504, theinconsistent data, a task, and/or a priority for first query 502A, asdescribed above.

Based on the first query 502A and the second query 504B, resolutionsystem 500 may create a first instance and a second instance,respectively, in a queue. The first instance and the second instance maybe in the same queue or in different queues. In some embodiments, theresolution system 500 may assign the first query 502A and the secondquery 504A to a queue based on one or more of the identified queryingentity, inconsistent data, task, and/or priority. For example, the firstquery 502A and the second query 504A may be assigned to the same queueif the identified tasks for the queries are the same. As anotherexample, the first query 502A and the second query 504A may be assignedto different queues because the querying entities are different.

In some embodiments, the first query 502A and the second query 502B maybe assigned to the same queue, and resolution system 500 may select oneof first query 502A and second query 504B from the queue based on theidentified priorities. For example, where first query 502A was receivedby resolution system 200 before second query 504A, first query 502A mayhave a higher priority than second query 504A and may be selected beforesecond query 504A. As another example, where the task identified forfirst query 502A has an earlier deadline than the task identified forsecond query 504A, first query 502A may have a higher priority thansecond query 504A and may be selected before second query 504A.

In some embodiments, resolution system 500 may select first query 502Aand initiate resolution of the inconsistent data of first query 502A.For example, resolution system 500 may, based on the identified task forfirst query 502A, generate a graphical user interface configured forresolution of the inconsistent data of first query 502A. Through thegraphical user interface, resolution system 500 may receive inputs, suchas inputs from an operator of resolution system 500. Alternatively oradditionally, through the graphical user interface, resolution system500 may provide outputs, such as outputs to an operator of resolutionsystem 500. The inputs and outputs may take any of the forms describedabove. Still alternatively or additionally, resolution system 500 mayretrieve information associated with the query from a remote entity. Forexample, resolution system 500 may retrieve information from datasource(s) 506 through one or more requests 506A, as shown. The graphicaluser interface may include the retrieved information, the inputs, and/orthe outputs, as described above.

Through the graphical user interface, an operator of resolution system500 may accomplish the task identified for the first query 502A. Whileaccomplishing the task, resolution system 500 may generate each of adocumentation and a resolution, as described above. Resolution system500 may store the documentation in, for example, data storage 508 at508A. Alternatively or additionally, resolution system 500 may publishthe documentation to one or more entities, such as first querying entity502, another querying entity such as second querying entity 504, one ormore data source(s) 506, or another entity. Resolution system 500 mayfurther publish 502B the resolution to first querying entity 502. Forexample, resolution system 500 may send the resolution (e.g., adocumentation describing the resolution) to first querying entity 502through a webpage or mobile application, by e-mail, mail, fax, ortelephone. In some embodiments, resolution system 500 may store theresolution as well.

In some embodiments, resolution system 500 may further select secondquery 504A and initiate resolution of the inconsistent data of secondquery 504A. For example, resolution system 500 may, based on theidentified task for second query 504A, generate a graphical userinterface configured for resolution of the inconsistent data of secondquery 504A. Through the graphical user interface, resolution system 500may receive inputs and/or outputs, as described above Alternatively oradditionally, resolution system 500 may retrieve information associatedwith the query from a remote entity, as described above. The graphicaluser interface may include the retrieved information, the inputs, and/orthe outputs, as described above.

Through the graphical user interface, an operator of resolution system500 may accomplish the task identified for the second query 504A. Whileaccomplishing the task, resolution system 500 may generate each of adocumentation and a resolution, as described above. Resolution system500 may store and/or publish the documentation, as described above.Resolution system 500 may further publish 504B the resolution to secondquerying entity 504. For example, resolution system 500 may send theresolution (e.g., a documentation describing the resolution) to secondquerying entity 504 through a batch process. In some embodiments,resolution system 500 may store the resolution as well.

FIGS. 6A-6E illustrate exemplary graphical user interfaces in aresolution process, consistent with disclosed embodiments. The graphicaluser interfaces may be generated by a resolution system, such asresolution systems 104 and 200 described above.

The resolution system may maintain a queue of queries requestingresolution of inconsistent data, as described above. When a query isreceived, the resolution system may create an instance in a queue basedon the query. In some embodiments, the resolution system may assign anidentifier to the query, such as a query ID, and the instance mayinclude information received in the query. The resolution system mayfurther identify a task for the query, as described above. Based on thetask, the resolution system may generate a graphical user interface toaccomplish the task, such as graphical user interface 600 shown in FIG.6A.

As shown, graphical user interface 600 may include indications 602A,602B, and 602 C of information received in the query, such as an“Account Number” , a “Borrower Name”, and a “Disputer”. Graphical userinterface 600 could include indications of other information received inthe query as well, or information based on the information in the query,or other information. Graphical user interface 600 may further includean indication of a query ID 604 assigned to the query, as well as anindication of the task 606 identified for the query, as described above.

In some embodiments, graphical user interface 600 may include one ormore inputs to receive information about resolution of the query. Forexample, as shown, graphical user interface 600 may include a text-basedinput 608 to receive text describing the query and/or the resolutionprocess. For instance, as shown, an operator of the resolution systemmay use the text-based input 608 to provide text describing the queryand/or the resolution process, such as a manner in which the query wasreceived (“Query received by telephone”). Text provided through thetext-based input may be associated with the query and/or displayed inthe graphical user interface 600.

As another example, as shown, graphical user interface 600 may includean image-based input 610 to receive images describing the query and/orthe resolution process. The image-based input 610 may be configured toreceive images associated with the resolution process, such as imagesincluded in the query, images retrieved from other data sources,screenshots of graphical user interfaces used in the resolution process,and/or images generated as part of the resolution process, such asoutputs provided through the graphical user interfaces. In someembodiments, as shown in graphical user interface 612 in FIG. 6B, theimage-based input, when selected, may provide a pop-up window 614through which an operator of the resolution system can select a type ofimage to associate with the query. Images provided through theimage-based input may be associated with the query and/or displayed inthe graphical user interface 612.

FIG. 6C depicts another graphical user interface 616 that may begenerated by the resolution system. Graphical user interface 616 maysimilarly include text-based input 608 and image-based input 610. Asshown, graphical user interface 616 may include or more query images 618associated with the query. The query images 618 may include, forexample, images included with the query and/or images added through animage-based input, as described above. In some embodiments, the imagesmay include, for example, images of graphical user interface, e-mail,letter, or other instrument through which the query was received from aquerying entity or images of information received with the query, suchas images of a credit history. Other query images 618 are possible aswell.

Graphical user interface 616 may further include an input 620 throughwhich an operator of the resolution system may retrieve information foruse in resolving the query. In some embodiments, through input 620, theoperator may retrieve information associated with the query from datastorage (e.g., data storage 108 described above) and/or one or moreremote entities (e.g., data source(s) 106 described above), as describedabove. The retrieved information may include text-based and/orimage-based information associated with the query. Retrieved informationmay be associated with the query and/or displayed in graphical userinterface 616.

In some embodiments, resolution system may retrieve information bysending a request or query to the data storage and/or remote entitiesand receiving the information in response. While graphical userinterface 616 depicts an input 620 for retrieving information, in someembodiments some or all of the information may be retrieved by theresolution system without input from an operator. For example, theresolution system may automatically retrieve information from datastorage and/or remote entities based on the query and/or the identifiedtask.

FIG. 6D depicts another graphical user interface 622. As shown,graphical user interface 622 includes an output 624. Graphical userinterface 622 may similarly include text-based input 608 and image-basedinput 610. In some embodiments, the resolution system may generate theoutput based on the query, the querying entity, the inconsistent data,the identified task, one or more inputs, and/or some or all of theretrieved information. The output 624 may be a text-based output, suchas a description of the identified task and/or the querying entity.Alternatively or additionally, the output 624 may be an image-basedoutput, such as a chart or graph generated based on retrievedinformation. The output 624 may be associated with the query.

FIG. 6E depicts another graphical user interface 626. As shown,graphical user interface 626 may similarly include text-based input 608and image-based input 610. In some embodiments, graphical user interface626 may include an input 628 through which an operator of the resolutionsystem 628 may provide a resolution of the query. For example, theoperator may select the resolution from a drop-down menu and/or mayprovide a text-based input through input 628. Alternatively oradditionally, in some embodiments the resolution system may determinethe resolution automatically based on the query, the querying entity,the inconsistent data, the identified task, one or more inputs, and/orsome or all of the retrieved information, and graphical user interface626 may display the resolution. The resolution system may associate theresolution with the query and/or display the resolution in graphicaluser interface 626.

In some embodiments, graphical user interface 626 may further include aninput 630 through which an operator may provide a publication for thequery. For example, the operator may select one or more entities towhich the resolution should be published and/or one or more manners ofpublication from a drop-down menu and/or may provide a text-based inputthrough input 630. Alternatively or additionally, in some embodimentsthe resolution system may publish the resolution automatically based onthe query, the querying entity, the inconsistent data, the identifiedtask, one or more inputs, and/or some or all of the retrievedinformation, and graphical user interface 626 may display an indicationof the publication, such as an image-based description of thepublication (e.g., an image of a graphical user interface, e-mail,letter, or other instrument used to publish the resolution) and/or atext-based description of the publication (e.g., text naming a queryingentity to which the resolution was published and/or a date on which theresolution was published). The resolution system may associate thepublication with the query and/or display the publication in graphicaluser interface 626.

FIG. 7 illustrates an exemplary resolution 700 generated through aresolution process, consistent with disclosed embodiments. In someembodiments, resolution 700 may be generated based on one or more ofgraphical user interfaces 600, 612, 614, 622, and 626, text-based and/orimage-based inputs and outputs, retrieved information, the query ID, thequerying entity, and/or the identified task. Resolution 700 may take theform of a graphical user interface and/or other data provided through aweb page and/or a mobile application, information (e.g., a document)provided by e-mail, mail, and/or fax, or information provided bytelephone. Alternatively or additionally, resolution 700 may be datastored in data storage accessible by the resolution system and/or thequerying entity or other entities. The resolution 700 may take otherforms as well.

As shown, resolution 700 may include a description 702 of how theinconsistent data was resolved. Additionally, resolution 700 may includeother information associated with the query by the resolution systemduring the resolution process, such as the query, the querying entity,the inconsistent data, the identified task, one or more inputs, and/orsome or all of the retrieved information. Resolution 700 may includeother information as well.

FIG. 8 illustrates an exemplary documentation 800 generated through aresolution process, consistent with disclosed embodiments. In someembodiments, while accomplishing the task through graphical userinterfaces such as graphical user interfaces 600, 612, 614, 622, and626, the resolution system may continually associate the graphical userinterfaces, text-based and/or image-based inputs and outputs, retrievedinformation, a resolution, and a publication with the query. The querymay be further associated with the query ID, the querying entity, and/orthe identified task. For example, the resolution system may store indata storage (e.g., data storage 108) data describing and/or otherwiseindicating the graphical user interfaces, text-based and/or image-basedinputs and outputs, retrieved information, resolution, publication,query ID, querying entity, and/or identified task and associate thestored information with the query. The data and/or other information mayinclude, for example, text-based data and/or image-based data.

Based on some or all of the associated information, the resolutionsystem may generate documentation 800. In some embodiments, as shown inFIG. 8, documentation 800 may include an indication 802 of informationassociated with the query. The information may include, for example,information received with the query, information retrieved from anotherentity (e.g., data source(s) 108 or data storage 106), and/orinformation received as an input from an operator of the resolutionsystem, as described above. The information indicated by indication 802may describe, for example, the query, the querying entity, theinconsistent data, and/or other information.

Alternatively or additionally, in some embodiments documentation 800 mayinclude an indication 804 of one or more text-based inputs receivedthrough the graphical user interfaces. For example, indication 804 mayinclude an indication of text-based information provided by an operatorthrough an input (e.g. text-based input 608 described above) in agraphical user interface. As another example, indication 804 may includean indication of text-based information retrieved from one or moreentities, such as data source(s) 106 and/or data storage 108 describedabove. The text-based information may describe, for example, theinconsistent data, the task, and/or the resolution process.

Still alternatively or additionally, in some embodiments documentation800 may include an indication 806 of one or more image-based inputsreceived through the graphical user interfaces. For example, indication806 may include an indication of image-based information provided by anoperator through an input (e.g. image-based input 810 described above)in a graphical user interface. As another example, indication 806 mayinclude an indication of image-based information retrieved from one ormore entities, such as data source(s) 106 and/or data storage 108described above. As still another example, indication 806 may include anindication of the graphical user interfaces themselves and/orscreenshots of the graphical user interfaces. The image-basedinformation may describe, for example, the inconsistent data, the task,and/or the resolution process.

Still alternatively or additionally, in some embodiments documentation800 may include an indication 808 of one or more outputs providedthrough the graphical user interfaces. For example, indication 808 mayinclude an indication of a text-based and/or graphic representation(e.g., image, chart, graph, etc.) of some or all of the retrievedinformation. As another example, indication 808 may include anindication of the graphical user interfaces themselves and/orscreenshots of the graphical user interfaces. The text-based and/orgraphic representation may describe, for example, the inconsistent data,the task, and/or the resolution process.

Still alternatively or additionally, in some embodiments documentation800 may include an indication 810 of the resolution and/or thepublication associated with the query. For example, indication 810 mayinclude an indication of a text-based and/or graphic representation ofthe resolution and/or the publication, such as an image of thepublication, a description of the resolution, and/or text included inthe publication. The text-based and/or graphic representation maydescribe, for example, the inconsistent data, the task, and/or theresolution process.

It will be understood that the graphical user interfaces, publications,and documentations described above, including their contents, are merelyillustrative and are not meant to be limiting. That is, other graphicaluser interfaces, publications, and documentations, including theircontents, are possible as well.

In some examples, some or all of the logic for the above-describedtechniques may be implemented as a computer program or application or asa plug-in module or subcomponent of another application. The describedtechniques may be varied and are not limited to the examples ordescriptions provided.

Moreover, while illustrative embodiments have been described herein, thescope thereof includes any and all embodiments having equivalentelements, modifications, omissions, combinations (e.g., of aspectsacross various embodiments), adaptations and/or alterations as would beappreciated by those in the art based on the present disclosure. Forexample, the number and orientation of components shown in the exemplarysystems may be modified. Further, with respect to the exemplary methodsillustrated in the attached drawings, the order and sequence of stepsmay be modified, and steps may be added or deleted.

Thus, the foregoing description has been presented for purposes ofillustration only. It is not exhaustive and is not limiting to theprecise forms or embodiments disclosed. Modifications and adaptationswill be apparent to those skilled in the art from consideration of thespecification and practice of the disclosed embodiments. For example,while a financial service provider and merchant have been referred toherein for ease of discussion, it is to be understood that consistentwith disclosed embodiments other entities may provide such services inconjunction with or separate from a financial service provider andmerchant.

The claims are to be interpreted broadly based on the language employedin the claims and not limited to examples described in the presentspecification, which examples are to be construed as non-exclusive.Further, the steps of the disclosed methods may be modified in anymanner, including by reordering steps and/or inserting or deletingsteps.

Furthermore, although aspects of the disclosed embodiments are describedas being associated with data stored in memory and other tangiblecomputer-readable storage mediums, one skilled in the art willappreciate that these aspects may also be stored on and executed frommany types of tangible computer-readable media, such as secondarystorage devices, like hard disks, floppy disks, or CD-ROM, or otherforms of RAM or ROM. Accordingly, the disclosed embodiments are notlimited to the above described examples, but instead is defined by theappended claims in light of their full scope of equivalents.

1. A system comprising: a processor; and data storage comprisinginstructions that, when executed by the processor, cause the system toperform operations comprising: receiving a query requesting resolutionof inconsistent data stored by multiple entities; identifying a queryingentity and the inconsistent data based on the received query; assigningthe query to a queue, wherein the queue is selected from one of aplurality of queues based on at least one of the querying entity or theinconsistent data: based on the query, creating an instance in thequeue, wherein the instance identifies a priority and a task for thequery; based on the priority, selecting the query from the queue andinitiating resolution of the inconsistent data by generating a graphicaluser interface to accomplish the task, wherein accomplishing the taskcomprises receiving data from the multiple entities; while accomplishingthe task, generating each of (i) a documentation documenting theinconsistent data and the task and (ii) a resolution resolving theinconsistent data; storing the documentation; and publishing theresolution.
 2. The system of claim 1, further comprising a communicationdevice, wherein receiving the query comprises receiving the query viathe communication device.
 3. The system of claim 2, wherein publishingthe resolution comprises publishing the resolution via the communicationdevice.
 4. The system of claim 1, wherein receiving the query comprisesreceiving the query through a batch process.
 5. The system of claim 1,wherein receiving the query comprises receiving the query through anoptical character recognition process.
 6. The system of claim 1, whereinaccomplishing the task comprises obtaining information associated withthe query from a remote entity.
 7. The system of claim 1, wherein thegraphical user interface is configured to receive an input associatedwith the task and to generate an output associated with the task.
 8. Thesystem of claim 7, wherein the documentation documenting the taskcomprises the documentation describing the input associated with thetask.
 9. (canceled)
 10. The system of claim 9, wherein the documentationdocumenting the task comprises the documentation describing the outputassociated with the task.
 11. The system of claim 1, wherein thedocumentation documenting the task comprises the documentationdescribing the graphical user interface.
 12. The system of claim 1,wherein: the query is received from a querying entity; and publishingthe resolution comprises sending the resolution to the querying entity.13. The system of claim 12, wherein sending the resolution to thequerying entity comprises sending the resolution through a batchprocess.
 14. The system of claim 12, wherein sending the resolution tothe querying entity comprises generating a document describing theresolution.
 15. The system of claim 1, further comprising publishing thedocument.
 16. The system of claim 1, wherein the priority is identifiedbased on a date the query is received.
 17. The system of claim 1,wherein the priority is identified based on the task.
 18. The system ofclaim 1, wherein the documentation comprises an image.
 19. The system ofclaim 1, wherein the documentation is searchable based on the query. 20.The system of claim 1, wherein the documentation is searchable based onthe inconsistent data.
 21. The system of claim 1, wherein the query isassigned to the queue based on the querying entity and the inconsistentdata.